Alarm Categories

For IP devices that have automatic CESID updating enabled in the CESID Assignment form, this alarm indicates that the system has detected a CESID assignment problem. Alarm level is always minor. The alarm threshold is not configurable.

The system will generate a CESID alarm in the following instances:

• A new or known IP device has registered, but no CESID is available for the device.

• A device has moved, and no CESID is available for the device at its new location.

• A new or known device has registered, but the CESID in the CESID Assignment form is different from the CESID in the L2 to CESID Mapping form. In this case, both CESIDs are cleared by the system, which generates an alarm.

NOTE: The Layer 2 to CESID Mapping form is not applicable to MiVoice Business for Mitel Communications Suite (MCS) since Layer 2 switching is performed by an external Layer 2 switch.

• At system startup, one or more IP devices that have Automatic CESID Updating enabled but have no CESIDs assigned to them.

To address the alarm, assign CESIDs in the CESID Assignment form or the L2 to CESID Mapping form. Once all DN CESID assignments are made, the system will clear the alarm. To change an existing entry in the CESID Assignment form, see Modify a CESID.

Indicates that the Database Verification process detected one or more corrupted files in any of the following Berkeley databases: Management Layer (ML) System, ISDN, Applications, IP Networking, and Voicemail (excluding the EMEM data). The alarm is raised when database verification fails during

• a system start up,

• a manual or scheduled database audit, or

• a manual or scheduled backup.

Details of the alarm are stored in the /db/spyLog/alarms/auditAlarm file, which is renamed and can still be viewed after the alarm is cleared. The directory is removed only during an upgrade or full install.

Only one alarm (always major) is generated for any number of database audits.

An active audit alarm causes all system backup attempts to fail, so it must be cleared before running a backup.

The alarm persists after a system reboot. To clear the alarm, perform a system Restore, ensuring that you are restoring an uncorrupted database. Otherwise, the Audit Failure alarm will not clear and it will be regenerated during system start up.

NOTE: Fixing or removing corrupted files and running a clean DATABASE AUDIT does not clear an active Audit Failure alarm.

Indicates a system backup failure(s) on the local node. Details are stored in the /db/spyLog/alarms/backupAlarm file, which is renamed and can still be viewed after the alarm is cleared. The directory is removed only during an upgrade or full install.

The most common reasons for a backup failure are:

• An Audit Failure alarm already exists.

• Database verification fails during the backup.

• There is not enough disk space.

• Failure to copy files during the backup.

• Failure to create a .tar file during the backup.

Only one alarm (always Major) is generated for any number of backup failures. The alarm persists after a system reboot; it clears only after a system restore OR once  the Audit Failure alarm (if present) and other issues are cleared and the backup process completes successfully.

The alarm will not be generated for failures associated with the client PC's browsers or applications. For example, if for a manual backup, the "Local hard drive" is selected as the location of the backup file and the ftp process fails, the alarm will not be generated. Similarly, if the client application - MiVoice Enterprise Manager - fails to download the .tar file, the alarm will not be generated.

Indicates the presence of a Bootrom mismatch between the firmware version in an installed card and the firmware version on the system hard drive. If you receive this alarm after installing a new card in the system, the firmware in the installed card needs to be upgraded from the version on the system hard drive. Enter the UpgradeBootrom ALL command to upgrade the firmware. You MUST reset the system to have the upgraded firmware take effect.

These alarm categories are not valid and can be ignored.

There is a problem with the database file or a problem downloading it during a Restore or a problem bringing it in from RAM on a Reboot.

A persistent fault in the signal processing of a DS1 or CEPT link.

Only digital trunk links that have a Digital Link Descriptor programmed in the Digital Links Form are included in the system total as output by the Alarm maintenance command. Use the Show Faults maintenance command to identify the faulty links .  

NOTE: For Italian CAS, the delay period before the alarm is activated (the length of time that an intermittent link fault exists before it becomes a persistent fault and raises an alarm) is specified by entering a value between 0 and 360 seconds in the Digital Link Fault Delay Timer field of the Digital Link Descriptors form.

Indicates FPGA on DSP II needs to be updated. See FPGA for details on how to update it.

A DSP card is detected but cannot be properly loaded.

A percentage of DSP resources are unavailable.  The failure of one or more, but not all, DSPs results in a Minor alarm. Critical alarm indicates that all DSPs have failed. In the event of an alarm, reset the system as soon as possible. If the DSP continues to fail, replace the module.

NOTE: E2T Comms is not applicable to MiVoice Business for ISS.

The E2T card is unavailable (MXe III only). The alarm is raised if the hardware is detected and the E2T card does not respond. Failure to respond indicates that the TCP/IP socket that the RTC and E2T used communicate is down or the the E2T card failed to boot,  perhaps because the E2T bootline is incorrect; you can check the bootline revision in the Hardware Compute Cards form.

No alarm is raised if the E2T card is not detected. (MXe III controller only.)

A fan is unavailable (CX II, CXi II, MXe III, and AX controllers only).

One of the redundant hard disks is faulty. The MXe III controller supports a RAID (Redundant Array of Independent Disks) module with redundant hard disks.

Indicates the presence of a Field Programmable Gate Array (FPGA) mismatch between the firmware version in an installed card and the firmware version on the system hard drive. If you receive this alarm after installing a new card in the system, the firmware in the installed card needs to be upgraded from the version on the system hard drive. Enter the UpgradeBootrom ALL command to upgrade the firmware. You MUST reset the system to have the upgraded firmware take effect.

NOTE: If your MXe III/MXe III-L controller has an FPGA alarm, then you must power down and power up the system, instead of a reboot. For more information, see Chapter 6, Maintenance > Power Down the Controller in the Technician's Handbook, Release 9.1.

There is a problem with the Frequency-shift Keying (FSK) generator.

Indicates that the gateway trunk interface is down.

NOTE: This alarm category only applies to the EX controller.

Indicates an I2C bus failure between the MSP430 and the Alarm Card. This alarm category only applies to the AX controller.

Indicates that IP trunking has failed or that the E2T card is not functioning.

NOTES

• The E2T card is not applicable to MiVoice Business for ISS.

• Ensure that the DHCP options for the E2T card are programmed correctly.

• Ensure that the router is in service and configured correctly.

The system clears the alarm after the error condition is resolved and communication is re-established.

Only IP trunks programmed in the ICP/PBX Networking, XNET ICP/PBX Networking, and IP/XNET Trunk Groups forms are included in the system total as output by Alarm Details form and the Alarm maintenance command.

For the trunk to become unavailable, it must fail during an attempt to use it.

Indicates that a license violation event has been detected by the License Manager or Designated License Manager.

If a license violation event is left unresolved, its severity level escalates, which in turn increases its alarm level; see License Violation Handling for details. Unlike other alarms, no number or threshold level is provided for alarms that are based in license violation events.

The following table lists License Violation levels and their equivalent Alarm levels.  

Indicates the amount of stations unavailable as a percentage (%) of the system total. The following are included in the line total:

• All IP devices wiith a programmed DN in the Multiline Sets, Single Line Sets, Console forms, and Hot Desk Users.

• All ONS devices in the Analog Sets form (whether programmed with a DN or not) associated with an ASU

• All paging devices programmed in the Loudspeaker Paging form

• All PKMs

• All IP music sources (as of 3300 ICP Release 7.0, all systems by default are assigned 64 virtual Music on Hold circuits for embedded MOH, which are included in the count).

Applies to MiVoice Business Virtual, and MiVoice Business for Industry Standard Server only.

The APC-MXe has lost communications with the Media Gateway (RTC).

• Ensure that all internal IP addresses are programmed correctly.

• Ensure that the internal L2 Switch is operating properly.

NOTE: Layer 2 switching is not directly applicable to MiVoice Business for ISS since Layer 2 switching is performed by an external Layer 2 switch.

The system clears the alarm after the error condition is resolved and communication is re-established.

Indicates the unavailability level of Call Control memory expressed as a percentage (%) of the total Call Control memory.

Indicates the unavailability level of system memory expressed as a percentage (%) of the total system memory. The system takes appropriate actions based on the amount of free system memory. See SysMem Used (MB) alarm threshold.

Monitoring of the status of the fans, power supplies and temperature of the system is compromised. When convenient, attempt to recover by shutting down the system using the RESET SYSTEM maintenance command and when the system starts booting up, power it down. Leave it powered down for 30 seconds and then power up. If the problem persists, arrange for system repair.

Indicates an out of date MSP430 F/W. Please upgrade it with the UpgradeBootrom ALL command. After the successful upgrade, the system requires a reboot for the new F/W to take effect. Please note that the MSP430 F/W upgrade takes around 5 minutes. In case of ESM timeout while the command is being carried out, it is safe to reissue UpgradeBootrom ALL to verify the F/W upgrade status.

One or more network synchronization sources has lost synchronization with the master node of the network.

The NETSYNC source category will only appear if the system is not the master clock for the network.

The Network Gateway Security Access Module associated with a legacy ISDN Gateway has been tampered with or has failed.

A voice channel problem has been identified from the controller to the ASU.

Indicates that the POST memory test in U-Boot has failed.

A Power Supply Unit has a fault (MXe III and AX controller only). Replace unit to clear alarm.

An active DTMF receiver circuits on the active Peripheral Switch Matrix card has a fault. By default all MiVoice Business systems are assigned three DTMF receivers, each having 16 circuits for a total of 48 circuits.

A hard disk drive has a fault (MXe controller only).

The SATA RAID controller cable is missing or disconnected.

A System Data Synchronization (SDS) data distribution error error has occurred. See Viewing Data Distribution Alarms for details.

The system generates a minor alarm after the number of errors exceeds 100, and a major alarm after the number exceeds 1000.

A user has made three failed attempts to access the system through port 23 or a DISA trunk using an invalid username. Each time login fails, the user is locked out for 15 minutes and the event is recorded in the maintenance log. On the third failed login attempt, the alarm is generated.

NOTE: The alarm is generated by an invalid username. Attempting to log in with a valid username and an invalid password does not generate the alarm. Displaying the alarm by entering the Show Fault Security maintenance command is sufficient to clear it.

System Fail Transfer (SFT) The system fail transfer feature allows selected stations of the system (or portions of the system, according to the type of outage), to be transferred to certain trunks. Such transfer action is automatic in the event of a failure of the main power supply. zones have switched into SFT mode.

The link is not available due to a communications failure, failure to register, or a busy out or return to service maintenance command being launched.

If the task or component is suspended and present in the Task and Component Task Restart list, the system will reset on the Programmed Reboot Resource Recovery time cycle. See Programmed Reboot for more information.

The system performs the  following steps while monitoring tasks and components:

• If a non-critical task is suspended, a log is generated and a MAJOR alarm is raised. If configured, the system will be reset at the next resource monitoring reboot time.

• If a critical task is suspended, a log is generated and a CRITICAL alarm is raised. The system will reset immediately.

The System Identification module or i-button is not installed or is incorrect.

Indicates that the number of calls that require T.38 functionality has exceeded the number of T.38 licenses in the system.

Indicates an issue with the T.38 software/hardware/configuration (including licensing) on system startup.

Stratum 3 clock module in controller has failed.

System has overheated. Cool down system to clear alarm.

The Trunks category covers all analog trunks and all ACTIVE digital trunks. Active digital trunks mean that they are only counted in the total if they are assigned a Digital Link Descriptor in the Digital Links Form.

The Trunks - Used count in the System Capacity form should match the trunk count output by the Alarm maintenance command.

A percentage of voice mail ports are unavailable.

Additional DSP resources are not allocated when more than 20 voice mail ports are programmed. The alarm is generated after the next reboot following the programming of additional ports if they are not supported with additional DSPs; basic telephony requirements are the system priority.

Embedded voice mail application has failed to start. Possible causes include the voice mail prompt files are not installed properly, or the voice mail application is unable to communicate with MiVoice Business call control. This error generates a MAJOR alarm.